Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify KV store naming requirements. #23

Merged
merged 2 commits into from
Mar 24, 2025
Merged

Conversation

kpfleming
Copy link
Contributor

Because the provided name is used both to find the KV store using the API and in the Compute SDK to open the store, that name must be both the name of the KV store and the name of the resource-link which connects the service to it.

Because the provided name is used both to find the KV store using the
API and in the Compute SDK to open the store, that name must be both
the name of the KV store and the name of the resource-link which
connects the service to it.
@kpfleming kpfleming requested a review from harmony7 March 18, 2025 13:22
@harmony7
Copy link
Member

👀

@harmony7
Copy link
Member

You're right, although I think this was not my intent. for now I've accepted your suggestion, and also updated the README to allow you to use the fastly CLI to do the creation and linking (the README used REST APIs because these CLI commands didn't exist way back when).

@harmony7 harmony7 force-pushed the clarify-kv-store-name branch from 9864dc1 to 0f9494d Compare March 24, 2025 08:38
@harmony7 harmony7 merged commit 410d76b into main Mar 24, 2025
1 check passed
@harmony7 harmony7 deleted the clarify-kv-store-name branch March 24, 2025 08:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants